Skip to content

Adding Visual Test Report in Github Actions #7653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: dev-2.0
Choose a base branch
from

Conversation

Vaivaswat2244
Copy link

@Vaivaswat2244 Vaivaswat2244 commented Mar 21, 2025

Resolves #7618

This PR adds support for generating an HTML report to compare visual test results more effectively. The goal is to improve accessibility and readability of visual regression test outputs.

Changes:

  • Added a script to generate an HTML report summarizing visual test results.
  • The report includes expected screenshots and actual screenshots
  • Updated the workflow to run the added script after completion of tests
  • Edited the VisualTest.js to save the recorded screenshots to a folder actual-screenshots.
  • Then the generated html report is uploaded as an artifact.

Screenshots of the change:
This is the screenshot of the html page generated. It will show expected and Actual visuals of this.

image
@davepagurek @ksen0 Can you have a look at this?
You can go ahead in the Actions under Summary and download the report from artifacts section.

PR Checklist

@davepagurek
Copy link
Contributor

Nice work @Vaivaswat2244! I'm a little less familiar with github actions myself, @ksen0 and @limzykenneth, does this look OK to you?

@Vaivaswat2244
Copy link
Author

Hello @davepagurek @limzykenneth @ksen0

Just following up on this PR - I'm wondering if there's any additional feedback or if we should move forward with the implementation as is? If you'd prefer to explore alternative approaches first or if we are waiting for the pr05 project, I'd be happy to convert this to a draft PR in the meantime. Otherwise, I'm ready to address any feedback to get this merged.

@ksen0
Copy link
Member

ksen0 commented Apr 24, 2025

Thanks for your patience @Vaivaswat2244 ! I will have time next week (when the GSoC reviews are done:) to review this, though if someone else reviews this before their feedback is welcome. Sorry for the wait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants